Table Contents (.d file)
Choose this option to load table contents. The Data Dictionary alphabetically lists all the tables defined for you database. After you select the table or tables, the Data Dictionary opens the Load Data Contents for Some Tables dialog box, shown in Figure 10–4.
The Load Data Contents for Some Tables dialog box contains the following fields:
- Input Directory
- Include LOB
- Acceptable Error Percentage
- Output Errors to Screen
If you load table contents for a single table, the Data Dictionary displays a default name for the file from which you can load your table contents. This default file is always the name of the table dump file, usually the table name with a .d extension.
When you load the contents of more than one table, the Data Dictionary prompts you for a directory from which it loads the contents files. If you do not specify a directory, the Data Dictionary loads the files from the current directory. The Data Dictionary loads each table from the corresponding table-name.d file.
The Data Dictionary provides the option of specifying an LOB directory. If you select yes, the Data Dictionary prompts you to provide the name of the LOB directory.
The Data Dictionary prompts you for an acceptable error rate. As the Data Dictionary loads records from any files you designate, it might encounter data that cannot be loaded. For example, a record might have data that would cause a duplicate value to be stored for a unique key field. The Data Dictionary does not load the record. If you specify an error rate of 10 percent, the Data Dictionary must successfully load 90 records from every set of 100 records loaded. If the error rate exceeds the specified rate, the Data Dictionary terminates the load. The Data Dictionary places bad records in the table-name.e file.
The Data Dictionary provides you with the option to display error messages to your screen.
Note: You can move and reorganize data by performing a binary dump and load. The binary method improves the dump and load performance significantly because the data remains in binary format during the process. For more information about performing a binary dump and load, see Chapter 2, " Database tasks."